Hello!

Our Exchange infrastructure description, briefly:

1. Using Exchange 2013 CU7

2. 2 x MBX+CAS servers (EX1, EX2)

3. 2 x Edge servers (mx1, mx2)

4. DAG, 4 DBs

5. Hybrid Configuration: 200 local users, 15 cloud users

Our case: sometimes our users receive NDR while sending messages to existing mailboxes:

"Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'

For example, user sent 2 messages, first caused NDR, second was successfully delivered:

Get-MessageTrackingLog -Sender sender@domain.ru -Recipient recipient@domain.ru | fl EventId, Source, TimeStamp, EventData

EventId   : HAREDIRECT
Source    : SMTP
Timestamp : 15.04.2015 16:58:36
EventData : {[DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : RECEIVE
Source    : SMTP
Timestamp : 15.04.2015 16:58:36
EventData : {[FirstForestHop, EX1.local.domain.ru], [Oorg, domain.ru], [ProxiedClientIPAddress, 10.0.100.21], [Proxie
            dClientHostname, mx1.domain.ru], [ProxyHop1, EX1.local.domain.ru(192.168.0.11)], [DeliveryPriority, Normal]
            , [AccountForest, local.domain.ru]}

EventId   : AGENTINFO
Source    : AGENT
Timestamp : 15.04.2015 16:58:36
EventData : {[AMA, SUM|action=st|error=|atch=0], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : FAIL
Source    : ROUTING
Timestamp : 15.04.2015 16:58:36
EventData : {[DeliveryPriority, Normal], [Oorg, domain.ru], [AccountForest, local.domain.ru]}

EventId   : HAREDIRECT
Source    : SMTP
Timestamp : 15.04.2015 18:17:23
EventData : {[DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : RECEIVE
Source    : SMTP
Timestamp : 15.04.2015 18:17:23
EventData : {[FirstForestHop, EX2.local.domain.ru], [ProxiedClientIPAddress, 10.0.100.22], [ProxiedClientHostname,
            mx2.domain.ru], [ProxyHop1, EX2.local.domain.ru(192.168.0.12)], [DeliveryPriority, Normal], [AccountForest,
            local.domain.ru]}

EventId   : AGENTINFO
Source    : AGENT
Timestamp : 15.04.2015 18:17:23
EventData : {[AMA, SUM|v=0|action=|error=|atch=0], [AMA, EV|engine=M|v=0|sig=1.195.3371.0|name=|file=], [TRA, ETR|ruleI
            d=068e0c20-5de5-48e0-9b53-ea90e5deb5b9|st=12.12.2014 18:27:31|action=SetSCL|sev=1|mode=Enforce], [CompCost
             |AMA=0|ETR=0], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : SEND
Source    : SMTP
Timestamp : 15.04.2015 18:17:25
EventData : {[E2ELatency, 4.863], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel, Opportunistic], [
            DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

EventId   : DELIVER
Source    : STOREDRIVER
Timestamp : 15.04.2015 18:17:25
EventData : {[MailboxDatabaseName, IT], [Mailboxes, c1357fa5-52f2-4d16-8c70-09c9f9c4ab0e], [ToEntity, Hosted], [E2ELate
            ncy, 4.863], [DeliveryPriority, Normal], [AccountForest, local.domain.ru]}

How can I investigate this issue? 

• Edited by Turboon Friday, April 17, 2015 11:47 AM

Hi Turboon,

Thank you for your question.

Did this issue occur when mailbox was moved to office 365?

"Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found' could be occurred if the on-premises mail-enabled user who represents the moved mailbox isn't stamped correctly with the target address. The Exchange server generates an NDR message because the on-premises Active Directory Domain Services (AD DS) can't locate the user in order to route the mail correctly. We could add the target address, also known as the service routing address, to the mail-enabled user in the on-premises environment by the following steps:

1.        In a web browser on your local Exchange 2013 server, browse to the Exchange Admin Center,
2.        Click Recipients, and then click Mailboxes.
3.        Click the user, and then click Edit.
4.        Click Email Address, and then click Add, .
5.        Under Email Address, click SMTP, and then enter the email address. Use the <alias>@<domain>.mail.onmicrosoft.com format for the email address.
6.        Click OK, and then click Save.

We could refer to the following link:

https://support.microsoft.com/en-us/kb/2685437

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Hello Ed, Jim!

Thank you for your useful answers!

We really have one corrupted DC in a branch site. One question before restoration:

How can we adjust Exchange settings to get data from DCs in certain site (head office site)?

Thanks in advance.

• Marked as answer by Turboon 23 hours 23 minutes ago

Make sure your AD Sites and Services has correct mappings of subnets to sites.  Exchange will look to DCs in the same site unless none are available.  Make sure you have GCs in the same sit